Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).billing-action { edr edr_format_name [ wait-until-flow-ends ] | egcdr | exclude-from-udrs | radius | rf } +
edr_format_name must be the name of an existing EDR format, and must be a string of 1 through 63 characters in length.
Important: If the EDR format name supplied here is not configured in the EDR Format Configuration Mode, or has been deleted, the system accepts it without applying any EDR format for the billing action in this ACS service.wait-until-flow-ends: By default, the EDR is generated immediately after a ruledef hit results in this charging action. When this keyword is specified, no EDR is generated on a ruledef hit. When the flow ends, an attempt is made to generate an EDR with the format specified.
To generate an eG-CDR the accounting-mode CLI command in the APN Configuration Mode must be configured with the “none” option.
The format of enhanced G-CDRs is controlled by the inspector CLI command in Context Configuration Mode.
By default, statistics are accumulated on a per content ID basis for possible inclusion in UDRs. The exclude-from-udrs keyword causes the system to not include the packet’s statistics in UDRs.
Rf accounting is applicable only for dynamic and predefined rules that are marked for it. Dynamic rules have a field offline-enabled to indicate this. To mark a predefined rule as offline-enabled, use this keyword and the billing-records CLI in the Rulebase Configuration Mode.
billing-action edr charge1_format
rating-group coupon_id
coupon_id must be an integer from 0 through 65535.
Important: This rating-group overrides the content ID, if present in the same charging-action for the prepaid customer in DCCA. But only the content IDs will be used in eG-CDRs irrespective of the presence of rating-group in that charging-action.charge-units units
Default: 0; disables the counter, same as no charge-units
units is the value set for charging unit, and must be an integer from 1 through 65535.
Important: For more information on content ID, refer to the if-protocol command in the Ruledef Configuration Mode Commands chapter.charge-unit 1024
charge-volume { protocol { bytes | packet-length | packets } [ downlink | uplink ] | constant value }
Default: charge-volume ip bytes
protocol must be one of the following:
|
•
|
dns: Charge volume for DNS
|
|
•
|
ftp-control: Charge volume for FTP-Control
|
|
•
|
ftp-data: Charge volume for FTP-Data
|
|
•
|
http: Charge volume for HTTP
|
|
•
|
icmp: Charge volume for ICMP
|
|
•
|
imap: Charge volume for Internet Message Access Protocol (IMAP)
|
|
•
|
ip: Charge volume for IP
|
|
•
|
mms: Charge volume for MMS
|
|
•
|
pop3: Charge volume for POP3
|
|
•
|
rtp: Charge volume for RTP
|
|
•
|
rtsp: Charge volume for RTSP
|
|
•
|
sdp: Charge volume for SDP
|
|
•
|
secure-http: Charge volume for secure-https
|
|
•
|
sip: Charge volume for SIP
|
|
•
|
smtp: Charge volume for SMTP
|
|
•
|
tcp: Charge volume for TCP
|
|
•
|
udp: Charge volume for UDP
|
|
•
|
wsp: Charge volume for WSP
|
|
•
|
wtp: Charge volume for WTP
|
constant units
units is the value set for charging, and must be an integer from 0 through 65535.
If constant 3 is configured for every invocation of this Charging Action, the system adds 3 to the downlink/uplink volume counter, depending on the direction of packet.
For information on supported protocols see the Ruledef Configuration Mode Commands chapter.
If charge-volume rtp packets is configured, system computes volume amounts for different options for RTP as follows:
Important: Whenever service counts volume, it counts all packets that the relevant analyzers accepted.
Important: If a TCP packet is routed to the HTTP analyzer but there is no HTTP payload, then the TCP statistics will be updated but the HTTP statistics will not be updated (except for the “packets ignored by the HTTP analyzer” statistic).content-id content_id
content_id is the content ID specified for credit control service in an active charging service, and must be an integer from 1 through 65535.
If the specified Ruledef uses the if-protocol command to select a value for content ID, then the content_id specified through this command is not used for billing record generation.
Important: For more information on content-id, refer to the if-protocol command in the Ruledef Configuration Mode Commands chapter.content-id 23
flow action { conditional user-agent end-token end_token_name | discard [ downlink | uplink ] | readdress [ server ip_address ] [ port port_number ] | terminate-flow | terminate-session }
conditional user-agent end-token end_token_name
Conditionally redirects the HTTP packets matched to a configured user-agent to a specified URL. The user agent is configured using the redirect user-agent command in the Active Charging Service Configuration Mode.
end_token_name must be an alpha and/or numeric string of 1 through 32 characters in length, and is configured with this command to end the redirection condition.
downlink: Discards only downlink packets.
uplink: Discards only uplink packets.
ip_address must be the re-address server’s IP address, and must be an IPv4 address.
port_number must be the re-address server’s port number, and must be an integer from 1 through 65535.
When a re-address server is configured for a charging action, the show configuration command will show the readdress related configuration only if server address is configured. And the show configuration verbose command will show the readdress sever if configured, else will display “no flow action”.
url must be a string size of from 1 through 511 characters in http://search.com/subtarg/%3furl=#HTTP.URL# format.
%3furl=: specifies the delimiter “?url=” between URLs.
dynamic_field indicates the dynamic fields for redirect URLs.
charging-action ca_sip_redir
content-id 10
flow action redirect-url sip:test@sip.org
ruledef sip_req
rulebase plan1
This would mean any SIP request that hits the sip_req ruledef, would get redirected to the url given in ca_sip_redir. This involves creating a redirection packet with the following response line and “Contact” header in the response.
The following command resets quota retry timer upon redirection of flow to HTTP URL http://search.com/?url=#http://msn.com#:
flow action redirect-url http://search.com/%3url=#http://msn.com# clear-quota-retry-timer
flow idle-timeout idle_timeout
idle-timeout idle_timeout
idle_timeout must be an integer from 0 through 86400.
flow limit-for-bandwidth { { direction { downlink | uplink } peak-data-rate bps peak-burst-size bytes violate-action { discard | lower-ip-precedence } [ committed-data-rate bps committed-burst-size bytes [ exceed-action { discard | lower-ip-precedence } ] ] } | { id id } }
downlink: Flow of data towards subscriber.
uplink: Flow of data from subscriber.
peak-data-rate bps
bps must be an integer from 1 through 4294967295.
peak burst-size bytes
bytes must be an integer from 1 through 4294967295.
Important: It is recommended that this parameter be configured to at least the greater of the following two values: 1) 3 times greater than packet MTU for the subscriber connection, OR 2) 3 seconds worth of token accumulation within the “bucket” for the configured peak-data-rate.discard: Discard the packet
lower-ip-precedence: Transmit the packet after lowering the IP precedence
bps must be an integer from 1 through 4294967295.
committed-burst-size bytes
bytes must be an integer from 1 through 4294967295.
discard: Discard the packet
lower-ip-precedence: Transmit the packet after lowering the ip-precedence
id id
Important: This keyword is only available in StarOS 8.1 and later releases.
Important: If the exceed/violate action is set to “lower-ip-precedence”, the TOS value for the outer packet becomes “best effort” for packets that exceed/violate the traffic limits regardless of what the ip user-datagram-tos copy command is configured to. In addition, the lower-ip-precedence option may also override the ip qos-dscp command configuration. Therefore, it is recommended that command not be used when specifying this option.Details of the QoS Traffic Policing feature is available in the System Enhanced Feature Configuration Guide.
The following command sets an uplink peak data rate of 128000 bps and lowers the IP precedence when the committed-data-rate and the peak-data-rate are exceeded:
flow limit-for-bandwidth uplink peak-data-rate 128000 violate-action lower-ip-precedence
The following command sets a downlink peak data rate of 256000 bps and discards the packets when the committed-data-rate and the peak-data-rate are exceeded:
flow limit-for-bandwidth downlink peak-data-rate 256000 violate-action discard
limit must be an integer from 1 through 4000000000.
over-limit-action action_type
action_type must be one of the following:
discard: Discards the packets
redirect-url: Redirects the flow
terminate-flow: Terminates the flow to which this packet belongs
terminate-session: Terminates the session to which this packet belongs
flow limit-for-flow-type 1024 over-limit-action terminate-flow
ip tos { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | ef | lower-bits tos_value } [ uplink | downlink ]
afxx
lower-bits tos_value
Important: In StarOS 8.1 and later releases, this keyword is lower-bits tos_value. In StarOS 8.0, it is tos_value.tos_value must be an integer from 0 through 63.
ip tos be downlink
ip vlan range
range must be an integer from 1 through 4094.
ip vlan 500
nexthop-forwarding-address ipv4_address
ipv4_address must be the next-hop forwarding address for this charging action, and must be specified using the standard IPv4 dotted decimal notation.
The following command sets the next-hop forwarding address for the current charging action to 1.1.1.1:
nexthop-forwarding-address 1.1.1.1
qos-class-identifier identifier
Important: This command is controlled by the dynamic-qos-renegotiation license.interactive priority
priority specifies the traffic handling priority, and must be an integer from 1 through 3.
service-identifier service_id
[ no ] tft packet-filter packet_filter_name
packet_filter_name specifies the packet filter’s name, and must be a string of 1 through 63 characters in length.
The following command configures the packet filter filter23 to be sent to the MS:
tft packet-filter filter23
tos { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | ef | lower-bits tos_value } [ downlink | uplink ]
afxx
Specifies the use of an assured forwarding xx Per Hop Behavior (PHB).
lower-bits tos_value
Important: In StarOS 8.1 and later releases, this keyword is lower-bits tos_value. In StarOS 8.0, it is tos_value.value must be an integer from 0 through 63.
The following command sets the ToS to be for downlink packets:
Important: This command is license dependent. For more information please contact your local sales representative.xheader-format format_name
format_name must be a string of 1 through 63 characters in length.
Also, see xheader-format CLI command in the Active Charging Service Configuration Mode and the x-header Format Configuration Mode Commands chapters.
